Capturing snapshots of storage volumes

ABSTRACT

A method and apparatus for capturing a snapshot of storage volumes of a data capture group are disclosed. In the method and apparatus, a request to create a data capture group may be received and processed. The data capture group may have one or more storage volumes. Upon defining the data capture group, a snapshot of the storage volumes of the data capture group may be taken.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/924,335, filed Jun. 21, 2013, entitled “CAPTURING SNAPSHOTS OFSTORAGE VOLUMES,” the content of which is incorporated by referenceherein in its entirety.

BACKGROUND

The use of network computing and storage has proliferated in recentyears. The resources for network computing and storage are oftenprovided by computing resource providers who leverage large-scalenetworks of computers, servers and storage drives to enable clients,including content providers, online merchants and the like, to host andexecute a variety of applications and web services. The contentproviders and online merchants, who traditionally used on-site serversand storage equipment to host their websites and store and streamcontent to their customers, often forego on-site hosting and storage andturned to using the resources of the computing resource providers. Theusage of network computing allows content providers and onlinemerchants, among others, to efficiently and adaptively satisfy theircomputing needs, whereby the computing and storage resources used by thecontent providers and online merchants are added or removed from a largepool provided by a computing resource provider as need and depending ontheir needs.

Further, it is often important for the clients of a computing resourceprovider to be able to capture their data that is stored in alarge-scale network and used by a variety of servers and hosts. Forexample, an organization may retain data for the purpose of being ableto revert a system to a previous state. In addition, modern computersystems often utilize multiple storage volumes. Different volumes may beused for different types of data and/or to provide redundancy.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments in accordance with the present disclosure will bedescribed with reference to the drawings, in which:

FIG. 1 shows an example of capturing a snapshot of stored data;

FIG. 2 shows an example of users connected to a computing resourceservice provider;

FIG. 3 shows an example of a block data storage service in a computingresource service provider environment;

FIG. 4 shows a flow diagram of an example method for defining a datacapture group;

FIG. 5 shows a flow diagram of an example method for capturing a unifiedsnapshot of a data capture group;

FIG. 6 shows a flow diagram of an example method for capturing asnapshot of a data capture group;

FIG. 7 shows a flow diagram of an example method for modifying a datacapture group;

FIG. 8 shows a flow diagram of an example method for restoring asnapshot; and

FIG. 9 illustrates an environment in which various embodiments can beimplemented.

DETAILED DESCRIPTION

In the following description, various embodiments will be described. Forpurposes of explanation, specific configurations and details are setforth in order to provide a thorough understanding of the embodiments.However, it will also be apparent to one skilled in the art that theembodiments may be practiced without the specific details. Furthermore,well-known features may be omitted or simplified in order not to obscurethe embodiment being described.

Techniques described and suggested herein relate to creating a datacapture group having one or more storage volumes and capturing the oneor more storage volumes of the data capture group. In an embodiment, auser may receive a request from a user to create a data capture group.The request may include descriptive information associated with the datacapture group. A management service receives the request to create adata capture group and causes a command for creating an entry for thedata capture group to be issued. In some embodiments and after creatingthe data capture group, the management service may receive a request tocapture a snapshot of the storage volumes of the data capture group,where a snapshot or a capture of the data capture group is arepresentation of a data set stored by the volume(s) in the data capturegroup at a moment in time. Upon receiving the request to capture asnapshot of the storage volumes, the management service may cause acommand for capturing the data of the storage volumes to be issued. Uponissuing the command for capturing the data of the storage volumes, thedata of the storage volumes may be captured and stored in a destinationstorage service. In one embodiment, the snapshot data of the storagevolumes of the data capture group may be stored as one or morehomogeneous bodies or as one or more data objects in a storage service.The location of where the one or more homogeneous bodies or one or moredata objects are stored may be indicated in the descriptive informationor in the request for capturing the data capture group. In anotherembodiment, the snapshot of each storage volume of the data capturegroup may be stored in a uniquely addressable location of the storageservice.

The descriptive information of the data capture group may include anidentity associated with a storage volume of the data capture group, anidentity associated with a host of the storage volume or an identityassociated with a load balancer, where the association between the loadbalancer and one or more storage volumes of a data capture group may beindirect, though the hosts referenced by the load balancer. Thedescriptive information may also an indication of whether a unifiedsnapshot or a transient snapshot is sought or an indication of whether areference snapshot or a delta snapshot is sought. The descriptiveinformation may also include an identity of a destination storageservice in which the captured data may be stored, a retention period theduration of which the snapshot data is to be retained in the storageservice or a restoration location to which the snapshot data is to bestored when requested.

In another embodiment, the management service may receive a requestmodify the data capture group. The request to modify the data capturegroup may originate from a user. The request to modify the data capturegroup may be directed to the addition or removal of storage volumes fromthe data capture group. The request to modify the data capture group mayalso be directed to modifying the descriptive information associatedwith the data capture group including the retention time, thedestination storage service and the like.

In an embodiment, the management service may determine the identity ofone or more storage volumes of the data capture group based on thedescriptive information. In other words, in some embodiments, thedescriptive information may not explicitly identify the volumes in anassociated data capture group, but the descriptive information is usedto determine which set of volumes is in the data capture group, wherethe set may dynamically change over time. In some examples, themanagement service may identify the one or more storage volumes based onthe identity or function of a host of the one or more storage volumes orthe identity or function of a load balancer servicing a host of the oneor more storage volumes. Generally, the descriptive information mayidentify a characteristic of one or more volumes that is used todetermine which volume(s) is/are in the data capture group.

In another embodiment, the management service may receive a request torestore the captured data. The request may, for instance, specify thecaptured data to be restored by an identifier associated with a datacapture group. The request to restore the captured data may also includean indication of a location to which the captured data is to berestored. In yet another embodiment, the location to which the captureddata is to be restored may be specified in the descriptive information.The snapshot of the storage volumes of the data capture data may berestored as one or more homogeneous bodies or one or more data objectsthat individually or collectively represent the captured snapshot.Alternatively, the snapshot of each storage volume of the data capturegroup may be restored to an individual or independent restorationlocation. The location(s) to which the snapshot is restored may bespecified as part of the descriptive information or in the request torestore the data capture group.

In another embodiment, the management service may receive a request todelete a captured snapshot. The request to delete the captured snapshotmay include an identity associated with the captured snapshot. Uponreceiving the request to delete the captured snapshot, the managementservice may determine whether the snapshot that is requested to bedeleted serves as the basis or a reference for a delta snapshotdiscussed below. The management service may further cause a command fordeleting the captured snapshot from a storage service to be issued. Thedeleted snapshot may be that which is captured of one or more volumes ofthe data capture group or, alternatively, the deleted snapshot may bewhich is captured of all the volumes of the data capture group.

In network computing and storage, network resources for data processingand data storage are available to users and subscribers for performingtheir computing needs. The network resources may be used for a varietyof functions, such as web-related functions. For example, the networkcomputing resources may be used as computing platforms for runninghosts, such as email or web servers, whereas the network storageresources may be used for storing data used by the hosts, for example,web content used by the web server or archived emails used by the emailserver, or other general purpose data. Because the data processing anddata storage resources are network-based, the user's computing andstorage platform are decentralize and the user is provided with theflexibility to add additional processing and storage resourcedynamically as needed by borrowing or renting resources from a providerof network computing and storage resources. Further, the user isprovided with the flexibility to remove existing resource as the user'sdemand for the resources declines.

Regardless of where data storage resources are located in a network orwhere the data is stored, it is often important to capture a snapshot ofthe stored data and store the snapshot in a back-up location. Capturingthe data and storing a copy of the data may be performed for back-up,redundancy, regulatory purposes and the like. The data snapshot is maybe retained for a period of time, for example, a predefined period oftime, or indefinitely and may be accessed at a later time as needarises.

FIG. 1 shows an example of capturing a snapshot of stored data. A user102 is connected to a computing resource service provider 106 via anetwork 104. The user 102 may be a human-operated device, such as acomputer, tablet, smart phone and the like, or an automated deviceconfigured to operate in accordance with the embodiments describedherein. In addition, the user may be a network computer or a virtualmachine. The user 102 may communicate with the network 104 using anyconnection type, such as a wired, wireless or fiber optic connection andthe network, in turn, may communicate with the computing resourceservice provider 106 using connection type. Further, the user 102 may bea customer of the computing resource service provider or may be a userinteracting with the computing resource service provider on behalf of acustomer.

The network 104 may of any type, such as the Internet, an intranet or anInternet service provider (ISP) network. The computing resource serviceprovider 106 comprises a plurality of hosts 108 ₁, 108 ₂, . . . , 108_(m), (singularly referred to hereinafter as host 108 and collectivelyreferred to hereinafter as hosts 108 _(1-m)) and a plurality of storagevolumes 110 ₁, 110 ₂, . . . , 110 _(n), (singularly referred tohereinafter as storage volume 110 and collectively referred tohereinafter as storage volumes 110 _(1-n). Each storage volume 110 mayutilize the storage resources of one or more storage devices (notshown), such as hard disks with spinning magnetic media or solid statedrives. Further, the storage devices implementing a single storagevolume may comprise multiple different types of storage devices (e.g.,hard disks with spinning magnetic media or solid state drives. Thestorage devices may be part of or connected to the same network ordifferent networks and may have the same or different types of storageor the same or different manufacturers. A storage device may bededicated to a particular storage volume 110 or shared among one or morestorage volumes 110 _(1-n).

As described herein, the computing resource service provider 106 enablesthe processing and storage of data by providing computing and storageresource to the user 102. The host 108 may be a virtual computer systemthat uses computational resource provided by the computing resourceservice provider 106. The host 108 may be associated with one or morestorage volumes 110 ₁, and a storage volume 110 may be associated withone or more hosts 108 _(1-m). For example, host 108 ₁ is associated withthree storage volumes 110 ₁, 110 ₂, 110 ₃ and storage volume 110 ₅ isassociated with two hosts 108 _(2,m).

Further, one or more of the hosts 108 ₁, and one or more of the storagevolumes 110 _(1-n) may be utilized by the user 102. In the exampleillustrated in FIG. 1, the user 102 utilizes two hosts 108 _(1,2) andfive storage volumes 110 ₁₋₅ to utilize the services of the computingresource service provider 106. The five storage volumes 110 ₁₋₅ of theuser 102 may be captured and stored in a storage service 112 for back-upor any other purpose. The data of the captured storage volumes 110_(1-n) may be retained in the storage service 112 for a period of timeor indefinitely and may be later restored to the storage volumes or toanother storage space.

To enable capturing data from storage volumes 110 _(1-n), the user 102may define or specify the storage volumes 110 _(1-n) to be captured andother metadata or descriptive information associated with the capturingof the storage volumes 110 _(1-n) and may initiate the capturing of thestorage volumes by issuing an application programming interface (API)function call to the computing resource service provider 106. Initiationof the capturing may also occur pursuant to an automated process, suchas a process of the customer 102 or computing resource service provider106 that issues API function calls according to one or more triggers,such as the passage of a specified amount of time, a number of writeoperations, an amount of new data written, among others. The computingresource service provider 106 may cause the storage volumes 110 _(1-n)that are specified by the user 102 to be captured and to be stored inthe storage service 112. The storage volumes 110 _(1-n) may be capturedregardless of whether they use the storage resources of one storagedevice or plurality of storage devices as described herein.

In an embodiment, the host 108 provides computational resources on whichapplications may run. The host 108 may use dedicated hardware, such as acentral processing unit (CPU), a random access memory (RAM), buses, amemory controller and the like to enable the execution of applications.Alternatively, the host 108 may utilize a virtual computing platform,whereby applications that are executed on the virtual computing platformand decoupled from an underlying hardware using virtualization. In avirtual computing environment, hardware used for computing may bedistributed over a network instead of being localized. Virtualizationallows hardware components that are distributed over a network to beconsolidated and used to provide computing platforms for multiple hosts108 _(1-m). A computing resource service provider 106 may construct anetwork of hardware components that are situated in multiple locations.Further, the computing resource service provider 106 may utilize avirtualization layer that allows each host 108 to run on a shared poolof computational resources. As a result of virtualization, thedistributed computational resources upon which the host 108 is runappear as a unified computing system.

Each host 108 may be used to provide computational resources for aparticular service or application of the user 102. For example, a firsthost 108 ₁ may be a web server for the user 102 and may deliver webcontent to the user's 102 customers, whereas a second host 108 ₂ may bean application host and may provide web content to customers utilizingmobile devices to access the network 104.

As described herein, a host 108 may store data in one or more storagevolumes 110 _(1-n). For example, the first host 108 ₁ stores data instorage volumes 110 ₁₋₃ and the second host 108 ₂ stores data in storagevolumes 110 _(4,5). The storage volumes may be remote (e.g., across anetwork) from the hosts and communication between a host and a storagevolume may utilize one or more appropriate protocols, such as anInternet Small Computer System Interface (iSCSI). Storage volumes 110_(1-n) may also be added or disassociated from a host 108 dynamically oras needed by the host 108 and as provisioned by the computing resourceservice provider 106. The storage volumes 110 _(1-n) may utilize thestorage resources of storage devices that are part of or connected tothe same network or different networks.

In addition, each storage volume 110 may be associated with a volumeidentity (ID), which may be a logical identity or the storage volume 110may be identified based on the host 108 that uses the storage volume 110or the function performed by the host 108 that uses the storage volume110. For example, storage volumes 110 ₁₋₃ may be identified as being thestorage volumes used by the first host 108 ₁ or as being the storagevolumes used by the web server when the first host 108 ₁ is a webserver. The flexibility in identifying the storage volumes of the user102 allows for ease of identification of the storage volumes for whichthe user seeks to capture a snapshot. Identifiers may also be unique ina set of storage volumes, such as all storage volumes provided as aservice and/or all storage volumes associated with the customer.Uniquely identifying the storage volumes 110 ₁, independently of theirphysical location in a network allows for capturing data relevant to theuser regardless of the host 108 that uses the storage volumes 110_(1-n).

In addition to providing virtual computing resources for the hosts 108_(1-m), the computing resource service provider 106 may also include anon-demand storage service and an archival storage service where asnapshot of the data of captured storage volumes 110 _(1-n) may bestored as described with reference to FIG. 2.

FIG. 2 shows an example of users connected to a computing resourceservice provider. The users 202 _(1-p) are connected to the computingresource service provider 206 via a network 204. Although one network204 is shown in FIG. 2, it is contemplated that the users 202 _(1-p) maybe connected to and may communicate with the computing resource serviceprovider 206 using any number of networks. The computing resourceservice provider 206 includes a virtual computing service 214, a blockdata storage service 216, an on-demand storage service 218, an archivalstorage service 220 and other virtual computing service 222.

The virtual computing service 214 provides a virtual computing platformon which hosts, such as hosts 108 _(1-m) described with reference toFIG. 1, may execute applications. The block data storage service 216 ofthe computing resource service provider 206 is a storage service thatmay include various storage volumes and may be distributed acrossmultiple networks. The block data storage service 216 provides users 202_(1-p) and hosts 108 _(1-m) with the capability to store data on anetwork.

The on demand storage service 218 and the archival storage service 220of the computing resource service provider 206 are further types ofstorage services provided by the computing resource service provider206. The on demand storage service 218 and the archival storage service220 may be used to store snapshots of data on the block data storageservice 216. The on demand storage service 218 and the archival storageservice 220 may differ in access time, reliability and cost. Forexample, data stored in the on demand storage service 218 may be morereadily available to the user 202 than the archival storage service 220and may have a lower retrieval or access time than data stored in thearchival storage service 220. However, due to the desirable features ofthe on demand storage service 218, the on demand storage service 218 mayhave a higher cost per storage unit than the archival storage service220 or a higher cost per read or write than the archival storage service220.

Other virtual computing service 222 may also be part of the computingresource service provider 206, which may provide additional computationresources for the users 202 _(1-p).

In order to facilitate capturing storage volumes that are used bymultiple hosts and that are disposed across one or more networks, theblock data storage service 216 may include a management service that isresponsible for receiving and processing requests for capturing orsnapshotting storage volumes and for causing the execution of capturingsnapshots of storage volumes and storing the snapshots in a storageservice. Further, the block data storage service 316 may includemetadata storage for storing descriptive information about the storagevolumes to be captured as described with reference to FIG. 3.

FIG. 3 shows an example of a block data storage service in a computingresource service provider environment. The block data storage service316 includes a customer interface 330 by which a user 302 interacts withthe block data storage service 316. The user 302 interacts with theblock data storage service 316 using a virtual machine that is run onvirtual computing service 314. Alternatively, the user 302 may be ahuman-operated device, such as a computer, that is equipped with aportal or interface by which the user 302 may execute function calls tothe block data storage service 316. The portal may be provided by theblock data storage service 316 for any number of users to manage theirstorage volumes and enable the capturing of a snapshot of the storagevolumes and the storage of the snapshot in a storage service.

The block data storage service 316 also includes a service interface322. The service interface enables the block data storage service 316 tocommunicate and to be connected with the virtual computing service 314,such as the virtual computing service 214 described with reference toFIG. 2 upon which hosts may be executed. Like the user 302, thefunctions of the service 324 may be executed on a virtual machine.

The block data storage service 316 includes a management service 324,metadata storage 326 and a block device network substrate 328. The blockdevice network substrate 328 is the underlying hardware of the storagevolumes and the block device network substrate 328 may comprise one ormore magnetic storage disks, solid state storage drives and the like.The block device network substrate 328 may be partitioned into one ormore storage volumes for use by the user 302 or the user's 302 hosts.

Data that is snapshot from storage volumes of the block device networksubstrate 328 may be stored in an on-demand storage service 318, anarchival storage service 320 or a customer storage service 340. In theexample of FIG. 3, the computing resource storage service includes anon-demand storage service 318 and an archival storage service 320 and,accordingly, communication between the block data storage service 316and the on-demand storage service 318 and the archival storage service320 is performed via the service interface 322. The customer storageservice 340 resides at the customer and may be on-premise and,accordingly, connectivity between the block data storage service 316 andthe customer storage service 340 is performed via the customer interface330.

The user 302 may have one or more hosts and one or more storage volumesthat utilize the resources of the computing resource service provider.The management service 324 facilitates capturing a snapshot of storagevolumes independently of the physical storage location of the storagevolumes and also across one or more hosts that utilize the storagevolumes. In contrast to other systems where the host is used to managecapturing a snapshot of the storage volumes and where only the storagevolumes that are used by the host may be snapshot, the managementservice 324 enables capturing a snapshot of multiple storage volumesthat are used by one or more hosts and that reside on one or morestorage devices.

The user may define a data capture group for capturing a snapshot ofstorage volumes.

The data capture group specifies one or more volumes that are relevantto the user or that the user seeks to capture. The user may senddescriptive information associated with the data capture group to themanagement service 324 of the block data storage service 316. Thedescriptive information may specify the storage volumes to be captured.The storage volumes may be specified using a volume ID of the storagevolumes, an identity of a host using the storage volumes to be captured,or the services performed by the host using the storage volumes (e.g., aweb server or an application host). In some embodiments and as describedherein, the storage volumes may also be identified by using an identityor a function associated with a load balancer that services the hosts ofthe storage volumes.

The descriptive information may also specify the destination storageservice in which the captured or snapshot storage volumes are to bestored, for example, the on-demand storage service 318, the archivalstorage service 320 or an on-premise customer storage service 340. Thedescriptive information may also include the duration or length of timethe data is to remain in the destination storage service. After theexpiration of the duration or length of time the data is to remain inthe destination storage service, the data will be erased from storageservice.

In addition, the descriptive information may also include an identity oran address associated of which the snapshot data is to be restored whenrequested. In some embodiments, the descriptive information may includea periodicity of snapshot capturing or a rate of snapshot capturing. Therate of snapshot capturing may define the number of snapshots per periodof time the user seeks to be captured, for example, one snapshot per dayor two snapshots per hour. The periodicity specifies a period of timethe maximum of which should not expire before snapshot capturing, forexample, thirty minutes. If the descriptive information does not includea periodicity or rate then a snapshot of the data may be captured uponrequest.

The descriptive information may also include an indication as to whetherthe desired snapshot is a “delta” snapshot or a reference snapshot. Adelta snapshot requires a reference snapshot in order for the deltasnapshot to be constructed. The delta snapshot represents a differencein data between the snapshot and another data set, for example, apreviously captured reference snapshot or both a previously captureddelta snapshot and a reference snapshot. A reference snapshot may be acomplete set of captured data and does not requires other captured datain order to be recovered. A reference and delta snapshot are analogousto a Moving Picture Experts Group (MPEG) encoded I-frame and P-frame,respectively.

The descriptive information may also include an indication of whether aunified snapshot or a transient is sought. A unified snapshot is asnapshot that is initiated while a storage volume is in a non-transientstate, which may be while input and output operations are ceased to thestorage volume. When input and output operations to the storage volumesare ceased, input and output operations are also ceased to the storagedevices whose resource are used by the storage volumes. A transientsnapshot, however, may be initiated while data is read from or writtento the storage volume. As recognized by those skilled in the art, uponretrieval, a transient snapshot may require processing before beingused. For example, before usage the transient snapshot may be verifiedto ensure data consistency or requisite checks may be performed on thetransient snapshot to ensure that the data may be used.

The user 302 may send a request to create or define a data capture groupto the management service 324. The request includes the descriptiveinformation indicating the storage volumes to be captured. Themanagement service 324 receives and processes the request to define thedata capture group and stores the descriptive information associated bythe request in the metadata storage 326. The management service maycreate an identity or a name for the data capture group and may use thename to associate the descriptive information with the data capturegroup defined by the user 302. In an embodiment, the user 302 definesthe identity or name of the data capture group and sends the identity orname to the management service 324. The name may be sent together withor as part of the request to create or define the data capture group,(e.g., using the API function call used to create or define the datacapture group), or in a separate message or API function call. Themanagement service 326 may use the name provided by the user toassociate the descriptive information of the data capture group in themetadata storage 326.

After creating of the data capture group, the management service 326 mayreceive requests for capturing storage volumes of the data capturegroup. The management service 326 uses the descriptive information heldin the metadata storage 326 for identifying the storage volumes to besnapshot and for managing the storage of the snapshot in a storageservice and the potential retrieval of the snapshot from the storageservice and placement of the retrieved snapshot.

The metadata storage 326 of the block data storage service 316 isadvantageous in that it holds descriptive information associated withdata capture groups regardless of the location in a network of thestorage volumes defined by the descriptive information or the hostsusing the storage volumes. The usage of the management service 324 andthe metadata storage 326 is in contrast to other systems, where due tothe absence of these entities, the creation data capture groups and thecapturing and storage of storage volumes defined by the data capturegroups is not feasible.

Upon receiving a request to capture the storage volumes, the managementservice 324 causes the storage volumes to be captured, for example, bycalling an API function or sending a message to the one or more hostsassociated with the storage volumes requesting that a snapshot of thestorage volumes be captured. Further, the management service 324 maysend a message or cause a function call to be sent to the block devicestorage substrate 328 requesting that a snapshot of the storage volumesbe captured and to the management service 324 or a storage service.

As described herein, the management service 324 may identify the storagevolumes to be captured using the request or the descriptive informationheld in the metadata storage 326. Before causing the data of the storagevolumes to be captured, the management service 326 may prepare thestorage volumes for snapshotting by ceasing input and output operationsor read and write operations to the storage volumes. To cease read andwrite operations to the storage volumes, the management service 326 mayinstruct the hosts using the storage volumes to suspend the operations.However, as described herein, instead of capturing the storage volumesin a steady state, ceasing the read and write operations may be forgoneand a snapshot of one or more storage volumes in a transient state maybe captured.

FIG. 4 shows a flow diagram of an example method for defining a datacapture group. In the method 400, a user defines a data capture group402. As described herein, defining the data capture group includessetting forth descriptive information associated with the data capturegroup. The descriptive information may include the volume IDs of thestorage volumes to captured, the destination storage device in which thecaptured data of the storage volumes is to be stored, a duration of timethe length of which the data is to be stored in storage volumes and aname associated with the data capture group, among others. The user maybe a human operated computer that is equipped with a portal that allowsthe user to enter the descriptive information associated with the datacapture group. The user 302 then sends a request to define the datacapture group to the block data storage service 316 404. For example,the human operator of a computer may command the portal to create thedefined data capture group and the portal, in turn, may cause an APIfunction to be called to the block data storage service 316, which isrouted to the management service 324. Upon receiving the request todefine the data capture group, the management service 324 may processthe request to define the data capture group. In addition to definingthe data capture group, the request to define the data capture group mayalso indicate a request to capture data.

Upon receiving the request to create the data capture group, themanagement service 324 identifies the purpose of the request andretrieves the descriptive information from the request. The managementservice 324 instructs the metadata storage 326 to create an entry forthe data capture group. The entry may include a portion of or all of thedescriptive information as formatted or processed by the managementservice 324. The entry for the data capture group may also includeadditional information other than that which is included in thedescriptive information.

After the request is received and processed, the management servicesends a notification to the user 302 indicating that the data capturegroup has been defined. The notification may be routed by the block datastorage service 316 to the user via the customer interface. The user 302then receives the notification indicating the data capture group hasbeen defined 406. The user may receive the notification as a message oralert on the portal used to send the request to create the data capturegroup. In an embodiment, where the descriptive information did notinclude a name associated with the data capture group, the notificationmay also include an identity or a name for the data capture group.

In another embodiment, the descriptive information provided by the userfor defining the data capture group may include identifying informationfor a storage volume other than a volume ID. For example, storagevolumes may be defined by the name or functionality of their associatedhost, for example, the user's web server, application server or both.Instead of including in the descriptive information the volume IDs ofthe storage volumes associated with either server, the descriptiveinformation may instead specify the host utilizing the storage volumes.Accordingly, the descriptive information may specify the storage volumesas the volumes of the application server or the volumes of the webserver.

To identify the storage volume IDs, the management service 324 may querythe service 314. The management service 324 may provide the service 314with the identity of the host associated with the storage volumes andmay receive, in return, the volume ID of the storage volumes. Further,in the event that the descriptive information identified the host by thefunctionality the host provides to the user 302, the management service324 may query the service 314 to identify the volumes IDs associatedwith the host that provide the particular function to the user 302. Forexample, the management service 324 may request the identification ofthe storage volumes used by the email server or the application serverof the user 302. Similarly, the management service 324 may query theservice to identify the volume ID used by the hosts of a particular loadbalancer. Alternatively, based on the descriptive information, themanagement service 324 may query the block device network substrate 328,a host or the user 302 in order to identify the storage volumes that arerequested to be captured.

Upon defining the data capture group, the data of the storage volumesmay be captured as described with reference to FIG. 5. FIG. 5 shows aflow diagram of an example method for capturing a unified snapshot of adata capture group. In the example method for capturing a unifiedsnapshot of a data capture group 500, a management service, such asdescribed herein with reference to FIG. 3, receives a request to capturea snapshot of a data capture group 502, whereby the request identifiesthe data capture group. The request may be received from a user 302. Therequest may identify the data capture group by a data capture groupname, storage volume IDs, host identity or functionality or loadbalancer identity or functionality. The management service thenidentifies the storage volumes to be captured 504 based on the requestand proceeds to capture a snapshot of the storage volumes. To ensurethat a unified snapshot is taken, the management service causes inputand output operations to the storage volumes to be suspended to paused506. The management service 324 may instruct one or more hosts of aparticular volume to suspend input and output operations to the storagevolume. After the input and output operations are paused, the managementservice initiates capturing the snapshot 508. The management servicedetects that snapshot capturing is complete 510 (for example, afterwaiting for a period of time) and notifies the user that snapshotcapturing is complete 512.

After snapshot capturing is completed, the snapshot is sent to a storageservice where a copy of the snapshot will be held for future retrieval.The management service may instruct the storage service to retain thecaptured snapshot for a duration of time. The management service mayreceive the captured snapshot from the storage volumes and send thecaptured snapshot to the storage service or, alternatively, themanagement service may instruct the storage volumes to send the capturedsnapshot to the storage service directly. The captured snapshot may bestored as one or more homogeneous bodies or as one or more data objectsthat individually or collectively represent the captured snapshot. Themanagement service may indicate to the storage service the location orlocations of where the one or more homogeneous bodies or one or moredata objects are to be stored. As another example, the storage servicemay independently determine the storage locations. Alternatively, thesnapshot of each storage volume of the data capture group may beindividually or in an independent location.

As described herein, a snapshot may be captured while input and outputoperations are suspended (also referred to herein as a unified snapshotor a consistent snapshot). Alternatively, the snapshot may be capturedregardless of whether input and output operations are performed to thestorage volumes. When a consistent snapshot is taken, the managementservice may identify the one or more hosts that read and write data tothe storage volumes and instruct the one or more hosts to cease inputand output operations while the pertinent data is captured.

In an embodiment, the one or more hosts may each use a command queue inwhich instructions that are slated for execution by the one or morehosts are prioritized. Prioritizing the instructions in the commandqueue ensures that the commands are sequentially executed by a host. Dueto the sequential execution of instructions, input and output operationsmay be suspended by placing an instruction for capturing a storagevolume ahead of read and write instructions in the command queue. Theplacement of the instruction for capturing a storage volume may thusensure that data capturing is initiated before any input or outputoperations. It is noted that in some embodiments, the command queue maybe implemented as a scheduler.

FIG. 6 shows a flow diagram of an example method for capturing asnapshot of a data capture group. In the example method for capturing asnapshot of a data capture group 600, management service 324 identifiesthe host for a storage volume 602 and determines whether a unifiedsnapshot is sought 604. The management service 324 may determine whethera unified snapshot is sought based on the descriptive information or mayresort to a default configuration if the descriptive information doesnot specify whether a unified snapshot is sought. For example, themanagement service 324 may be configured to command capturing a deltasnapshot unless it is instructed otherwise.

If the management service 324 determines that a positive determinationis sough, the host is put in a state to take a unified snapshot 606. Asdescribed herein, the host is put in a state to take a unified snapshotby suspending input and output operation to a storage volume. Themanagement service 324 then initiated snapshot capturing 608 anddetermines whether snapshot capturing is completed before the expirationof a time limit 610. To determine whether snapshot capturing iscompleted before the expiration of a time limit, the management service324 may start a timer and determine whether a captured snapshot isreceived prior to the expiration of the timer.

If snapshot capturing is completed before the expiration of the timelimit, the management service 324 causes input and output operations tothe storage volumes to be resumed 612 and the snapshot is sent to astorage service 614. If snapshot capturing is not completed before theexpiration of the time limit, the management service performs asubsequent initiation of snapshot capturing 608.

If, however, the management service 324 determines that a unifiedsnapshot is not sought, the management service 324 initiates snapshotcapturing 616 without putting the host in a state to take a unifiedsnapshot. The management service 324 then determines whether snapshotcapturing is completed before the expiration of a time limit 618. Ifsnapshot capturing is completed before the expiration of the time limitthen the snapshot is sent to a storage service 620. If, however,snapshot capturing is not completed before the expiration of the timelimit, the method 600 reverts to a subsequent initiation of snapshotcapturing 616.

In addition to or instead of determining whether snapshot capturing iscompleted before the expiration of a time limit, the management serviceor, as may be contemplated in other embodiments, another entity of theblock data storage service 316 may determine whether a captured snapshotis erroneous. If a captured snapshot is determined to be erroneous,snapshot capturing may be reinitiated as described with reference toFIG. 6. A snapshot may be deemed erroneous if, for example, the snapshotfails an error detection scheme, such as a hash function or a redundancycheck.

A user may add or remove storage volumes to a host dynamically as theneeds of the user change. For example, in intervals of heavy web trafficstorage volumes may be added to a host functioning as a web server. Theaddition or removal of storage volumes used by a host may necessitatemodifying a data capture group accordingly. In addition to modifying thestorage volumes of the data capture group, the user may request themanagement service to modify the retention period of a snapshot, thedestination storage service of the snapshot and the like. To modify anexisting data capture group, the user sends a request for modifying thedata capture group to the management service 324 as described withreference to FIG. 7.

FIG. 7 shows a flow diagram of an example method for modifying a datacapture group. In the method 700, the management service receives arequest to modify the data capture group from the user 302 702. Therequest to modify the data capture group may be performed as an APIfunction call by the user. The request includes an identity of the datacapture group and the descriptive information that is requested to bemodified. The request to modify the data capture group may include arequest for the addition of storage volumes to the data capture group,the removal of volumes from the data capture group, a change to theretention period of a snapshot or the destination storage service of thesnapshot or a preferred restoration location for restoring the snapshotstorage volumes, among others. As with defining the data capture group,the user may identify storage volumes for modifying the data capturegroup using a volume identity, the name or functionality of a host ofthe storage volumes, the name or functionality of a load balancer thatservices a host of the storage volumes.

The management service 324 modifies the descriptive informationassociated with the data capture group in the metadata storage 326 inaccordance with the request 704. If needed, the management service mayalso identify the storage volumes that are requested to be modified. Themanagement service then sends a notification to the user indicating thatthe data capture group has been modified 706.

After the modification of the data capture group subsequent requests tocapture a snapshot will be based on the modified data capture group. Torevert to a previously defined data capture group, the user may requestfurther modification to the data capture group.

After a snapshot is stored, the user may seek to restore the snapshot.For instance, the snapshot may serve as a backup copy of the user's dataand the user may seek to restore the snapshot due to data failure or thesnapshot may have been taken for a regulatory purpose and the user mayseek to restore the snapshot for user access. The user may send arequest to the management service to restore the snapshot, whereby theuser may specify the location to which the data is to be restored in therequest or the location may be specified in the descriptive informationassociated with the data capture group. The snapshot of the storagevolumes of the data capture data may be restored as one or morehomogeneous bodies or one or more data objects that individually orcollectively represent the captured snapshot. Alternatively, thesnapshot of each storage volume of the data capture group may berestored to an individual or independent restoration location. Thelocation(s) to which the snapshot is restored may be specified as partof the descriptive information or in the request to restore the datacapture group.

FIG. 8 shows a flow diagram of an example method for restoring asnapshot. The management service receives a request to restore asnapshot 802. The request to restore the snapshot may include a name oridentity associated with the data capture group or a name or identityassociated with the captured snapshot that is sought to be restored. Itis noted that the name or identity of a captured snapshot may beprovided by the management service to the user upon the snapshot beingcaptured. The name or identity of a captured snapshot may be used todistinguish different snapshots. For example the captured snapshotidentity may be used to distinguish two snapshots of the same datacapture group that were captured at different points in time.

The management service determines whether the retention periodassociated with the snapshot has expired 804. If it is determined thatthe retention period has expired, the management service 324 notifiesthe user that the request cannot be processed 806. The notification mayinclude a code indicating that the request cannot be processed due tothe expiration of the retention period.

If, on the other hand, it is determined that the retention period hasnot expired, then the management service identifies the storage servicewhere data is held 808 and the data is provided for use 810, forexample, by restoring the data from the storage service to a storagelocation specified by the user. Then a notification is sent to the userindicating that the data is ready for use 812. It is noted that thelocation to which the data is restored may be identified by the user inthe request to restore the snapshot or may be a part of the descriptiveinformation of the data capture group.

The user may request the management service to delete a capturedsnapshot. Using a portal of the computing resource service providerexecuted on a computer, a human operator may, for example, requestdeleting captured snapshot by identifying the snapshot and causing acommand to be sent to the management service. The management service mayidentify the storage service storing the snapshot and may, in turn,cause a second command to be executed requesting the management serviceto delete the snapshot. The management service may identify the snapshotto be deleted. Further, before sending the command, the managementservice may verify the lack of any delta snapshots that are captured asdependent on the snapshot sought to be deleted. After the verificationis completed, the management service may request deletion of thecaptured snapshot. If a delta snapshot if found to depend upon thesnapshot sought to be deleted, the management service may notify theuser or request user confirmation of the request for deletion. Uponreceipt of the confirmation, the management service may delete thesnapshot.

In an embodiment, the user may request the management service to providethe user with status information associated with the data capture group.Using a portal of the computing resource service provider executed on acomputer, a human operator may, for example, request receiving statusinformation associated with the data capture group by identifying thedata capture group and causing a command, such as an API call, to besent to the management service. The user may receive the descriptiveinformation associated with the data capture group as statusinformation. Further, the user may also receive a log detailing thecaptured snapshot of the data capture group. The portal may cause thestatus information to be displayed on the computer as a result of therequest to provide the user with the status information.

FIG. 9 illustrates aspects of an example environment 900 forimplementing aspects in accordance with various embodiments. As will beappreciated, although a web-based environment is used for purposes ofexplanation, different environments may be used, as appropriate, toimplement various embodiments. The environment includes an electronicclient device 902, which can include any appropriate device operable tosend and receive requests, messages or information over an appropriatenetwork 904 and convey information back to a user of the device.Examples of such client devices include personal computers, cell phones,handheld messaging devices, laptop computers, tablet computers, set-topboxes, personal data assistants, embedded computer systems, electronicbook readers, and the like. The network can include any appropriatenetwork, including an intranet, the Internet, a cellular network, alocal area network, or any other such network or combination thereof.Components used for such a system can depend at least in part upon thetype of network and/or environment selected. Protocols and componentsfor communicating via such a network are well known and will not bediscussed herein in detail. Communication over the network can beenabled by wired or wireless connections and combinations thereof. Inthis example, the network includes the Internet, as the environmentincludes a web server 906 for receiving requests and serving content inresponse thereto, although for other networks an alternative deviceserving a similar purpose could be used as would be apparent to one ofordinary skill in the art.

The illustrative environment includes at least one application server908 and a data store 910. It should be understood that there can beseveral application servers, layers or other elements, processes orcomponents, which may be chained or otherwise configured, which caninteract to perform tasks such as obtaining data from an appropriatedata store. Servers, as used herein, may be implemented in various ways,such as hardware devices or virtual computer systems. In some contexts,servers may refer to a programming module being executed on a computersystem. As used herein the term “data store” refers to any device orcombination of devices capable of storing, accessing and retrievingdata, which may include any combination and number of data servers,databases, data storage devices, and data storage media, in anystandard, distributed, or clustered environment. The application servercan include any appropriate hardware and software for integrating withthe data store as needed to execute aspects of one or more applicationsfor the client device, handling some (even a majority) of the dataaccess and business logic for an application. The application server mayprovide access control services in cooperation with the data store andis able to generate content such as text, graphics, audio, and/or videoto be transferred to the user, which may be served to the user by theweb server in the form of HyperText Markup Language (“HTML”), ExtensibleMarkup Language (“XML”), or another appropriate structured language inthis example. The handling of all requests and responses, as well as thedelivery of content between the client device 902 and the applicationserver 908, can be handled by the web server. It should be understoodthat the web and application servers are not required and are merelyexample components, as structured code discussed herein can be executedon any appropriate device or host machine as discussed elsewhere herein.Further, operations described herein as being performed by a singledevice may, unless otherwise clear from context, be performedcollectively by multiple devices, which may form a distributed system.

The data store 910 can include several separate data tables, databasesor other data storage mechanisms and media for storing data relating toa particular aspect of the present disclosure. For example, the datastore illustrated may include mechanisms for storing production data 912and user information 916, which can be used to serve content for theproduction side. The data store also is shown to include a mechanism forstoring log data 914, which can be used for reporting, analysis or othersuch purposes. It should be understood that there can be many otheraspects that may need to be stored in the data store, such as for pageimage information and to access right information, which can be storedin any of the above listed mechanisms as appropriate or in additionalmechanisms in the data store 910. The data store 910 is operable,through logic associated therewith, to receive instructions from theapplication server 908 and obtain, update or otherwise process data inresponse thereto. In one example, a user, through a device operated bythe user, might submit a search request for a certain type of item. Inthis case, the data store might access the user information to verifythe identity of the user and can access the catalog detail informationto obtain information about items of that type. The information then canbe returned to the user, such as in a results listing on a web page thatthe user is able to view via a browser on the user device 902.Information for a particular item of interest can be viewed in adedicated page or window of the browser. It should be noted, however,that embodiments of the present disclosure are not necessarily limitedto the context of web pages, but may be more generally applicable toprocessing requests in general, where the requests are not necessarilyrequests for content.

Each server typically will include an operating system that providesexecutable program instructions for the general administration andoperation of that server and typically will include a computer-readablestorage medium (e.g., a hard disk, random access memory, read onlymemory, etc.) storing instructions that, when executed by a processor ofthe server, allow the server to perform its intended functions. Suitableimplementations for the operating system and general functionality ofthe servers are known or commercially available and are readilyimplemented by persons having ordinary skill in the art, particularly inlight of the disclosure herein.

The environment in one embodiment is a distributed computing environmentutilizing several computer systems and components that areinterconnected via communication links, using one or more computernetworks or direct connections. However, it will be appreciated by thoseof ordinary skill in the art that such a system could operate equallywell in a system having fewer or a greater number of components than areillustrated in FIG. 9. Thus, the depiction of the system 900 in FIG. 9should be taken as being illustrative in nature and not limiting to thescope of the disclosure.

The various embodiments further can be implemented in a wide variety ofoperating environments, which in some cases can include one or more usercomputers, computing devices, or processing devices which can be used tooperate any of a number of applications. User or client devices caninclude any of a number of general purpose personal computers, such asdesktop, laptop, or tablet computers running a standard operatingsystem, as well as cellular, wireless, and handheld devices runningmobile software and capable of supporting a number of networking andmessaging protocols. Such a system also can include a number ofworkstations running any of a variety of commercially-availableoperating systems and other known applications for purposes such asdevelopment and database management. These devices also can includeother electronic devices, such as dummy terminals, thin-clients, gamingsystems, and other devices capable of communicating via a network.

Various embodiments of the present disclosure utilize at least onenetwork that would be familiar to those skilled in the art forsupporting communications using any of a variety ofcommercially-available protocols, such as Transmission ControlProtocol/Internet Protocol (“TCP/IP”), protocols operating in variouslayers of the Open System Interconnection (“OSI”) model, File TransferProtocol (“FTP”), Universal Plug and Play (“UpnP”), Network File System(“NFS”), Common Internet File System (“CIFS”), and AppleTalk. Thenetwork can be, for example, a local area network, a wide-area network,a virtual private network, the Internet, an intranet, an extranet, apublic switched telephone network, an infrared network, a wirelessnetwork, and any combination thereof.

In embodiments utilizing a web server, the web server can run any of avariety of server or mid-tier applications, including Hypertext TransferProtocol (“HTTP”) servers, FTP servers, Common Gateway Interface (“CGP”)servers, data servers, Java servers, and business application servers.The server(s) also may be capable of executing programs or scripts inresponse requests from user devices, such as by executing one or moreweb applications that may be implemented as one or more scripts orprograms written in any programming language, such as Java®, C, C#, orC++, or any scripting language, such as Perl, Python, or TCL, as well ascombinations thereof. The server(s) may also include database servers,including without limitation those commercially available from Oracle®,Microsoft®, Sybase®, and IBM®.

The environment can include a variety of data stores and other memoryand storage media as discussed above. These can reside in a variety oflocations, such as on a storage medium local to (and/or resident in) oneor more of the computers or remote from any or all of the computersacross the network. In a particular set of embodiments, the informationmay reside in a storage-area network (“SAN”) familiar to those skilledin the art. Similarly, any necessary files for performing the functionsattributed to the computers, servers or other network devices may bestored locally and/or remotely, as appropriate. Where a system includescomputerized devices, each such device can include hardware elementsthat may be electrically coupled via a bus, the elements including, forexample, at least one central processing unit (“CPU” or “processor”), atleast one input device (e.g., a mouse, keyboard, controller, touchscreen or keypad) and at least one output device (e.g., a displaydevice, printer or speaker). Such a system may also include one or morestorage devices, such as disk drives, optical storage devices andsolid-state storage devices such as random access memory (“RAM”) orread-only memory (“ROM”), as well as removable media devices, memorycards, flash cards, etc.

Such devices also can include a computer-readable storage media reader,a communications device (e.g., a modem, a network card (wireless orwired), an infrared communication device, etc.), and working memory asdescribed above. The computer-readable storage media reader can beconnected with, or configured to receive, a computer-readable storagemedium, representing remote, local, fixed, and/or removable storagedevices as well as storage media for temporarily and/or more permanentlycontaining, storing, transmitting, and retrieving computer-readableinformation. The system and various devices also typically will includea number of software applications, modules, services, or other elementslocated within at least one working memory device, including anoperating system and application programs, such as a client applicationor web browser. It should be appreciated that alternate embodiments mayhave numerous variations from that described above. For example,customized hardware might also be used and/or particular elements mightbe implemented in hardware, software (including portable software, suchas applets), or both. Further, connection to other computing devicessuch as network input/output devices may be employed.

Storage media and computer readable media for containing code, orportions of code, can include any appropriate media known or used in theart, including storage media and communication media, such as, but notlimited to, volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage and/or transmissionof information such as computer readable instructions, data structures,program modules, or other data, including RAM, ROM, ElectricallyErasable Programmable Read-Only Memory (“EEPROM”), flash memory or othermemory technology, Compact Disc Read-Only Memory (“CD-ROM”), digitalversatile disk (DVD), or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage, or other magnetic storage devicesor any other medium which can be used to store the desired informationand which can be accessed by the system device. Based on the disclosureand teachings provided herein, a person of ordinary skill in the artwill appreciate other ways and/or methods to implement the variousembodiments.

The specification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense. It will, however, beevident that various modifications and changes may be made thereuntowithout departing from the broader spirit and scope of the invention asset forth in the claims.

Other variations are within the spirit of the present disclosure. Thus,while the disclosed techniques are susceptible to various modificationsand alternative constructions, certain illustrated embodiments thereofare shown in the drawings and have been described above in detail. Itshould be understood, however, that there is no intention to limit theinvention to the specific form or forms disclosed, but on the contrary,the intention is to cover all modifications, alternative constructionsand equivalents falling within the spirit and scope of the invention, asdefined in the appended claims.

The use of the terms “a” and “an” and “the” and similar referents in thecontext of describing the disclosed embodiments (especially in thecontext of the following claims) are to be construed to cover both thesingular and the plural, unless otherwise indicated herein or clearlycontradicted by context. The terms “comprising,” “having,” “including,”and “containing” are to be construed as open-ended terms (i.e., meaning“including, but not limited to,”) unless otherwise noted. The term“connected,” when unmodified and referring to physical connections, isto be construed as partly or wholly contained within, attached to orjoined together, even if there is something intervening. Recitation ofranges of values herein are merely intended to serve as a shorthandmethod of referring individually to each separate value falling withinthe range, unless otherwise indicated herein and each separate value isincorporated into the specification as if it were individually recitedherein. The use of the term “set” (e.g., “a set of items”) or “subset”unless otherwise noted or contradicted by context, is to be construed asa nonempty collection comprising one or more members. Further, unlessotherwise noted or contradicted by context, the term “subset” of acorresponding set does not necessarily denote a proper subset of thecorresponding set, but the subset and the corresponding set may beequal.

Conjunctive language, such as phrases of the form “at least one of A, B,and C,” or “at least one of A, B and C,” unless specifically statedotherwise or otherwise clearly contradicted by context, is otherwiseunderstood with the context as used in general to present that an item,term, etc., may be either A or B or C, or any nonempty subset of the setof A and B and C. For instance, in the illustrative example of a sethaving three members used in the above conjunctive phrase, “at least oneof A, B, and C” and “at least one of A, B and C” refers to any of thefollowing sets: {A}, {B}, {C}, {A, B}, {A, C}, {B, C}, {A, B, C}. Thus,such conjunctive language is not generally intended to imply thatcertain embodiments require at least one of A, at least one of B and atleast one of C to each be present.

Operations of processes described herein can be performed in anysuitable order unless otherwise indicated herein or otherwise clearlycontradicted by context. Processes described herein (or variationsand/or combinations thereof) may be performed under the control of oneor more computer systems configured with executable instructions and maybe implemented as code (e.g., executable instructions, one or morecomputer programs or one or more applications) executing collectively onone or more processors, by hardware or combinations thereof. The codemay be stored on a computer-readable storage medium, for example, in theform of a computer program comprising a plurality of instructionsexecutable by one or more processors. The computer-readable storagemedium may be non-transitory.

The use of any and all examples, or exemplary language (e.g., “such as”)provided herein, is intended merely to better illuminate embodiments ofthe invention and does not pose a limitation on the scope of theinvention unless otherwise claimed. No language in the specificationshould be construed as indicating any non-claimed element as essentialto the practice of the invention.

Preferred embodiments of this disclosure are described herein, includingthe best mode known to the inventors for carrying out the invention.Variations of those preferred embodiments may become apparent to thoseof ordinary skill in the art upon reading the foregoing description. Theinventors expect skilled artisans to employ such variations asappropriate and the inventors intend for embodiments of the presentdisclosure to be practiced otherwise than as specifically describedherein. Accordingly, the scope of the present disclosure includes allmodifications and equivalents of the subject matter recited in theclaims appended hereto as permitted by applicable law. Moreover, anycombination of the above-described elements in all possible variationsthereof is encompassed by the scope of the present disclosure unlessotherwise indicated herein or otherwise clearly contradicted by context.

All references, including publications, patent applications and patents,cited herein are hereby incorporated by reference to the same extent asif each reference were individually and specifically indicated to beincorporated by reference and were set forth in its entirety herein.

What is claimed is:
 1. A computer-implemented method for capturingsnapshots, the method comprising: receiving descriptive informationdefining a data capture group that includes a plurality of storagevolumes, the descriptive information indicating a set of characteristicsto identify devices in the data capture group that have thecharacteristics; creating, in a metadata storage, an entry based atleast in part on the descriptive information; receiving a request tocapture a snapshot of the data capture group; and in response to therequest, for each storage volume form the plurality of storage volumes:at a time when input/output operations to the storage volume are active,causing a transient snapshot capture command to be issued for thestorage volume to capture a transient snapshot of the storage volumewhile the storage volume is in a transient state.
 2. The method of claim1, wherein the descriptive information identifies the plurality ofstorage volumes.
 3. The method of claim 1, further comprising:determining an identity associated with the plurality of storage volumesbased at least in part on an identity or function of one or more hostsusing the plurality of storage volumes; and wherein the identity orfunction of the one or more hosts using the plurality of storage volumesis received in the descriptive information.
 4. The method of claim 1,further comprising, for each storage volume form the plurality ofstorage volumes, causing the snapshot to be sent to a storage service.5. The method of claim 4, further comprising: receiving a request torestore the snapshot; in response to the request to restore thesnapshot, for each storage volume form the plurality of storage volumes:causing the snapshot to be obtained from the storage service; andcausing the snapshot to be provided to a second storage service.
 6. Themethod of claim 5, wherein causing the snapshot to be obtained from thestorage service includes obtaining an individual snapshot of eachstorage volume from the plurality of storage volumes.
 7. Acomputer-implemented method for capturing snapshots, the methodcomprising: receiving a request to create a data capture group includinga plurality of storage volumes, the request indicating a set ofcharacteristics to identify devices in the data capture group that havethe characteristics; creating an entry, in a metadata storage, for thedata capture group; receiving a request to capture a snapshot of thedata capture group; and in response to the request, for each storagevolume in the data capture group, causing a command to capture a deltasnapshot of at least one storage volume of the plurality of storagevolumes to be issued, the delta snapshot identifying a difference indata between the delta snapshot and at least a previously capturedreference snapshot of the data capture group.
 8. The method of claim 7,wherein the request specifies one or more characteristics that definethe data capture group by being common to each storage volume in thedata capture group.
 9. The method of claim 7, wherein the request tocreate the data capture group includes descriptive informationassociated with the data capture group, wherein the descriptiveinformation indicates an identity associated with at least one storagevolume of the plurality of storage volumes.
 10. The method of claim 7,further comprising: detecting, independent of a customer request, achange to the data capture group; at a time after detecting the changeto the data capture group, receiving a second request to capture asnapshot of the data capture group; and in response to the secondrequest, for each storage volume in the changed data capture group,causing the command to capture a snapshot of at least one storage volumeof the plurality of storage volumes to be issued.
 11. The method ofclaim 10, wherein: the method further comprises: receiving a request todelete the data capture group; and updating metadata to indicatedeletion of the data capture group; and one or more individual snapshotsof each storage volume in the data capture group before the request todelete are persistently stored after updating the metadata.
 12. Themethod of claim 7, further comprising: detecting that the capturedsnapshot is erroneous; and in response to detecting that the capturedsnapshot is erroneous, causing the command to reinitiate capturing thesnapshot to be issued for each storage volume in the data capture group.13. A computing resource service provider for capturing a snapshot ofone or more storage volumes, the computing resource service providercomprising: a block data storage service comprising: one or more storagevolumes; and metadata storage; and a management service configured to:receive a request to create a data capture group from a user, the datacapture group including the one or more storage volumes from the blockdata storage service, the request indicating a set of characteristics toidentify devices in the data capture group that have thecharacteristics; create an entry for the data capture group in themetadata storage; initiate capturing a delta snapshot of the datacapture group, the delta snapshot identifying a difference in databetween the delta snapshot and at least a previously captured referencesnapshot of one or more storage volumes from the block data storageservice of the data capture group; and store the snapshot in a storageservice.
 14. The computing resource service provider of claim 13,wherein the snapshot is a type of snapshot from a plurality of snapshottypes, including a unified snapshot type, the management service iscapable of causing to be taken.
 15. The computing resource serviceprovider of claim 13, wherein the storage service is an archival storageservice, an on-demand storage service or a customer on-premise storageservice.
 16. The computing resource service provider of claim 13,wherein the management service is further configured to: determinewhether the snapshot is captured before expiration of a time limit; andin response to the snapshot not being captured before the expiration ofa time limit, reinitiate capturing the snapshot for each volume in thedata capture group.
 17. The computing resource service provider of claim13, wherein: the request to create the data capture group specifics astorage volume characteristic; and the management service is furtherconfigured to determine the one or more storage volumes as a result ofthe one or more storage volumes sharing the storage volumecharacteristic.
 18. The computing resource service provider of claim 13,wherein: initiating capturing a snapshot of the data capture groupincludes initiating an individual snapshot for each storage volume inthe data capture group; and the management service is further configuredto, for each storage volume in the data capture group, pauseinput/output operations prior to initiating an individual snapshot forthe storage volume.
 19. The computer-implemented method for capturingsnapshots of claim 1, wherein the transient snapshot comprises a deltasnapshot that identifies a difference in data between the delta snapshotand at least a previously captured reference snapshot.
 20. Thecomputer-implemented method for capturing snapshots of claim 19, whereinthe delta snapshot identifies a difference in data between the deltasnapshot and at least the previously captured reference snapshot and apreviously captured second delta snapshot.